RFC0036: Protocol Notes
Network Working Group S. Crocker Request for Comments: 36 16 March 1970 Protocol Notes I Overview -------- The network protocol provides three facilities: 1. Connection ...
RFC0442: Current flow-control scheme for IMPSYS
Network Working Group V. Cerf Request for Comments: 442 24 January 1973 NIC: 13774 The Current Flow-Control Scheme for IMPSYS BB&N quarterly report #13 outlines part of the current flow control sc...
RFC0449: Current flow-control scheme for IMPSYS
Network Working Group Dave Walden RFC # 449 BBN-NET NIC # 14133 Jan. 6, 1973 Updates RFC 442 The Current Flow-control Scheme for IMPSYS. ...
RFC0529: Note on protocol synch sequences
Network Working Group A. McKenzie Request for Comments: 529 B. Thomas NIC: 17165 R. Tomlinson References: RFCs 454, 513, BBN-TENEX ...
RFC0054: Official Protocol Proffering
Network Working Group Steve Crocker (UCLA) Request for Comments # 54 Jon Postel (UCLA) June 18, 1970 John Newkirk (Harvard) Mike Kraley (Harvard) ...
RFC5578: PPP over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics
Independent Submission B. Berry, Ed. Request for Comments: 5578 S. Ratliff Obsoletes: 4938 E. Paradise Category: Informational Cisco IS...
RFC0055: Prototypical implementation of the NCP
Network Working Group J. Newkirk Request for Comments: 55 M. Kraley Harvard J. Poste...
RFC5626: Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)
Network Working Group C. Jennings, Ed. Request for Comments: 5626 Cisco Systems Updates: 3261, 3327 R. Mahy, Ed. Category: Standards Track Unaffiliated ...
RFC5666: Remote Direct Memory Access Transport for Remote Procedure Call
Internet Engineering Task Force (IETF) T. Talpey Request for Comments: 5666 Unaffiliated Category: Standards Track B. Callaghan ISSN: 2070-1721 Apple ...
RFC0059: Flow Control - Fixed Versus Demand Allocation
Edwin W. Meyer, Jr. MIT Project MAC 27 June 1970 The method of flow control described in RFC 54, prior allocation of buffer space by the use of ALL network commands, has one particular advantage. If no more t...
RFC0060: A Simplified NCP Protocol
Network Working Group R. Kalin Request for Comments: 60 MIT 13 July 1970 A Simplified NCP Protocol Abstract This RFC d...
RFC0626: On a possible lockup condition in IMP subnet due to message sequencing
Network Working Group L. Kleinrock (UCLA-NMC) Request for Comments: 626 H. Opderbeck (UCLA-NMC) NIC #22161 Mar 1974 "On a Possible Lockup Condition in th...
RFC0632: Throughput degradations for single packet messages
Network Working Group H. Opderbeck Request for Comments: #632 UCLA-NMC NIC # 30239 20 May 1974 Throughput Degradations for Single Packet Messages The transmissi...
RFC0635: Assessment of ARPANET protocols
Network Working Group Vinton G. Cerf Request for Comments: 635 Stanford University NIC: 30489 An Assessment of ARPANET Protocols ABSTRACT This paper presents some theoretical and...
RFC0761: DoD standard Transmission Control Protocol
RFC: 761 IEN: 129 ...
RFC6529: Host/Host Protocol for the ARPA Network
Independent Submission A. McKenzie Request for Comments: 6529 S. Crocker Category: Historic April 2012 ISSN: 2070-1721 Host/Host Protocol for the ARPA Network ...
RFC0675: Specification of Internet Transmission Control Program
Network Working Group Vinton Cerf Request for Comments: 675 Yogen Dalal NIC: 2 Carl Sunshine INWG: 72 December 1974 ...
RFC0892: ISO Transport Protocol specification
Network Working Group ISO Request for Comments: 892 December 1983 ISO Transport Protocol Specification This document is distributed as an RFC for information only. It does not specify a standard for the ARPA Inte...
RFC7016: Adobe's Secure Real-Time Media Flow Protocol
Internet Engineering Task Force (IETF) M. Thornburgh Request for Comments: 7016 Adobe Category: Informational November 2013 ISSN: 2070-1721 Adobe's Secure Real-Time Media Flow Protoco...
RFC0071: Reallocation in Case of Input Error
Network Working Group Tjaart Schipper Request for Comments #71 25 September 1970 UCLA-CCN Reallocation in Case of Input Error In case of reading a message from...